chore(master): release 0.8.0 - #648

✅ No new issues found.

Reviewed changes — no prior pullfrog review existed on this PR, so this run covers it end to end: the release-please commit plus the follow-up lockfile regeneration.

• Cut 0.7.0 → 0.7.1 across the manifest and workspace — .release-please-manifest.json's "." entry, workspace.package.version, and every # x-release-please-version dep pin in Cargo.toml moved together.
• Generated the 0.7.1 changelog section — 8 entries spanning one feature, four refactors, one doc fix, and two asset chores.
• Regenerated Cargo.lock for the bump — a pure version-line change (59 insertions / 59 deletions) covering every workspace member.

What I checked, since a release PR's failure mode is an omission rather than a bad line:

• Changelog completeness — all 8 non-merge commits landed on master since 4261efff ("release 0.7.0") are present (#647, #634, #649, #650, #651, #652, #653, #654). Nothing missing, nothing extra.
• Bump correctness — 0.7.1 is a patch despite feat(vm) (#653) because release-please-config.json sets bump-patch-for-minor-pre-major: true. That matches the configured intent rather than misclassifying the feature.
• Version consistency — no # x-release-please-version line is left at 0.7.0, and the only two version = "0.7.0" entries remaining in Cargo.lock are the third-party rustls-platform-verifier and system-configuration. sdk/rust (published as arcbox) rides version.workspace and moved with the rest.
• Independent cadences held still, correctly — arcbox-hv (0.3.20), arcbox-helper (1.1.0), and arcbox-fleet-agent (0.1.4) all stayed put, as did the fleet / sdk/typescript / sdk/python manifest entries.
• Release config untouched — draft and force-tag-creation are still set on the root package only, so the documented draft-until-assets-exist ordering is intact.

ℹ️ Nitpicks

• The #653 changelog line reads "make the dmsetup search list configuration" where "configurable" was clearly intended. It mirrors the merged commit subject verbatim, so release-please will regenerate it and an edit to CHANGELOG.md on this branch wouldn't survive another bot run — the durable place to correct it is the draft GitHub release body, which stays editable until the tarball is attached and the release publishes.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

✅ No new issues found.

Reviewed changes

Since the previous review at 387bfd5, the delta is a single generated changelog line:

• refactor(computer): the sweep and pause reach a VM's area through the port (#686, 54c78f0), filed under ### Code Refactoring — the correct section for a refactor type. The 0.7.1 section goes 55 → 56 entries.

Re-verified against the new head:

• Changelog completeness — git log --no-merges 80513be2..origin/master returns exactly one commit (54c78f04), mapping 1:1 onto the one added entry. Nothing dropped, nothing invented.
• Base coverage — git merge-base origin/master HEAD equals origin/master (54c78f04); the release branch contains all of master.
• Version sweep — machine-checked across all 65 workspace members: workspace.package.version = 0.7.1, every # x-release-please-version pin at 0.7.1, and only the three documented independent cadences (arcbox-hv 0.3.20, arcbox-helper 1.1.0, arcbox-fleet-agent 0.1.4) ride their own versions. No 0.7.0 remains in Cargo.toml; the only 0.7.0 left in Cargo.lock are the third-party rustls-platform-verifier and system-configuration.
• Diff arithmetic — Cargo.lock is 62 + / 62 -, every one a standalone version = "0.7.1" line; Cargo.toml is 54 changed pairs with zero lines lacking 0.7.[01]; .release-please-manifest.json bumps the single "." key. Release date 2026-08-19 matches today (UTC). release-please-config.json is untouched.
• Publish shape — 54c78f04 touches 30 files, all .rs except one README; no Cargo.toml, no Cargo.lock, no protos. Its two added files (virt/arcbox-fc-driver/src/staging.rs, virt/arcbox-vm-driver/src/testkit/fake_staging.rs) sit under src/ in crates that carry no package.include, so packaging picks them up. Member count is still 65 and the set of six brand-new crates.io crates is unchanged, so the PublishNew rate-limit headroom established in the prior review still holds.

Worth noting: every crate this delta touches (arcbox-computer-runtime, arcbox-fc-driver, arcbox-vm-driver) is a first-time crates.io publish, and xtask is publish = false — so no already-published crate changed at all here, which makes the patch bump trivially accurate for this increment.

Note the usual head-SHA drift: the webhook payload carried f5f2c46, but chore: update lockfiles for release landed after it fired. This review covers a4357a7.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my last review (a4357a7, the 0.7.1 cut) is release-please re-cutting this release to 0.8.0 after a breaking change landed on master:

• Re-cut the release 0.7.1 → 0.8.0 — .release-please-manifest.json's ".", workspace.package.version, and all 53 # x-release-please-version dep pins moved together. The minor bump is the correct release-please outcome: #687 is refactor(computer)!, and even with bump-patch-for-minor-pre-major: true a BREAKING CHANGE still bumps the minor for pre-1.0. Since this PR never merged, no 0.7.1 exists anywhere, so the re-cut loses nothing.
• Added the ### ⚠ BREAKING CHANGES section carrying #687 ("the runtime stops naming an adapter, and the last two exceptions retire"), plus #687's matching entry under ### Code Refactoring — appearing in both sections is standard release-please behavior for a breaking commit. Section total is 57 type-section entries + 1 breaking = 58 bullets.
• Regenerated Cargo.lock for the bump — a clean 62 + / 62 -, every changed line a standalone version = "0.8.0" (62 == 65 members − 3 independent cadences).

Verified, since a release PR's failure mode is an omission:

• Changelog completeness — git log --no-merges 54c78f04..origin/master yields exactly one commit (86ac9e12, #687), mapping 1:1 onto the new entries, and git merge-base origin/master HEAD == origin/master == 86ac9e12. Nothing missing, nothing invented.
• The breaking-change label is accurate but bounded — the two refactor! items (VmmConfig → RuntimeConfig rename with no alias; removal of pub use arcbox_tap_net as network) are real API removals, but both live in arcbox-computer-runtime, a first-time crates.io publish at 0.8.0. computer/arcbox-computer (already published) is not in #687's file list, so no published API actually breaks; the 0.8.0 cascade to the other members is the workspace lockstep design already reviewed across thirteen prior runs.
• Lockfile fidelity — #687's arcbox-fc-driver dep swap (arcbox-vm-proto out, arcbox-constants in) shows as context in the full diff because the regen commit 1f2530d0 was rebuilt on master tip, not on the old branch; the lockfile commit 690d6ed7 touches version lines only.
• Version sweep — no 0.7.0/0.7.1 stragglers anywhere in workspace Cargo.toml files; the three independent cadences (arcbox-hv 0.3.20, arcbox-helper 1.1.0, arcbox-fleet-agent 0.1.4) correctly left alone.
• release-please-config.json untouched — draft + force-tag-creation still on the root package only.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/deepseek-ai/deepseek-v4-flash-0731 ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my last review (690d6ed7) is one changelog entry, a date move, and a fresh regen:

• One new ### Features entry — feat(computer): storage_bytes meters the retained footprint in every state (#692, 468ed81), taking the 0.8.0 section from 58 to 59 bullets. It maps 1:1 onto the single commit that landed on master since 86ac9e12, and the subject carries no breaking marker, so filing it under Features (not BREAKING CHANGES) is correct.
• Release date moved 2026-08-19 → 2026-08-20 — matches today.
• Regen rebuilt on top of the new master tip — the release-please regen (061848ce) and lockfile commit (f0a97b01) now sit on 468ed815; merge-base origin/master HEAD == origin/master == 468ed815, so nothing on the base branch is missing.

Re-verified against the new head:

• Changelog completeness — git log --no-merges 86ac9e12..origin/master yields exactly one commit (468ed815, #692), mapping 1:1 onto the one added entry. Nothing extra, nothing dropped.
• Version sweep — [workspace.package] and every # x-release-please-version dep pin at 0.8.0; zero 0.7.[01] remains in Cargo.toml; the only 0.7.0 left in Cargo.lock is the third-party rustls-platform-verifier / system-configuration pair.
• Lockfile fidelity — clean 62 + / 62 -, every changed line a standalone version = "0.8.0" (62 == 65 members − 3 independent cadences); arcbox-hv (0.3.20) and arcbox-helper (1.1.0) correctly left off the sweep.
• #692's footprint is publish-safe — 21 files, all .rs / proto comments / SDK surfaces; no Cargo.toml, no Cargo.lock, no new members. Member count stays 65, so the six-first-time-crates.io-crate set and the publish rate-limit headroom are unchanged.
• .release-please-manifest.json — "." at 0.8.0; fleet / sdk/typescript / sdk/python untouched. release-please-config.json not among the changed files.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/deepseek-ai/deepseek-v4-flash-0731 ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my last review (f0a97b01) is one generated changelog entry plus a fresh regen on the new master tip:

• One new ### Features entry — feat(computer): SandboxEvent carries a monotonic sequence number (#695, b38e943), taking the 0.8.0 section from 59 to 60 bullets total (59 type entries + 1 breaking). A feat type is correctly filed under Features.
• Release date unchanged — still 2026-08-20, matching today.
• Regen rebuilt on the new master tip — the release-please regen (1d8c9973) and lockfile commit (4c3aad78) now sit on b38e9435; merge-base origin/master HEAD == origin/master == b38e9435, so nothing on the base branch is missing. The regenerated Cargo.lock is byte-identical to the state verified at the prior review (62 + / 62 -, every changed line a standalone version = "0.8.0").

Re-verified against the new head:

• Changelog completeness — git log --no-merges 468ed815..origin/master yields exactly one commit (b38e9435, #695), mapping 1:1 onto the one added entry.
• Version sweep — [workspace.package] and all 53 # x-release-please-version dep pins at 0.8.0; the three independent cadences (arcbox-hv 0.3.20, arcbox-helper 1.1.0, arcbox-fleet-agent 0.1.4) correctly left off the sweep. Zero 0.7.x remains in Cargo.toml except third-party tokio-util 0.7.18, and the only 0.7.0 left in Cargo.lock is the documented third-party rustls-platform-verifier / system-configuration pair.
• #695's footprint is publish-safe — 27 files, all .rs / proto / SDK surfaces; no Cargo.toml, no Cargo.lock, no new members. The proto change is an additive field (sequence = 5 on SandboxEvent, buf breaking clean, no AGENT_PROTOCOL_VERSION bump per the commit message), and the three SDKs gain the field additively. Member count stays 65, so the six-first-time-crates.io-crate set and the publish rate-limit headroom carry forward.
• release-please-config.json untouched — draft + force-tag-creation remain on the root package only.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/deepseek-ai/deepseek-v4-flash-0731 ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my prior review (4c3aad78, sixteenth) is eight changelog entries plus a date move; the manifest, Cargo.toml, and Cargo.lock are unchanged in shape.

• Eight handover-lifecycle commits joined the 0.8.0 section (68 bullets total, up from 60) — one Features entry (b4244907, feat(computer): make a handover a lifecycle transition of its own), six Bug Fixes (773f67c, 38f3a6d, 005c5ba, 732730c, 4ea4a9f, 910bd1f), and one Code Refactoring (18d8c53). Each is filed under the section its conventional-commit type implies.
• Release date moved 2026-08-20 → 2026-08-21 — matching today.

What I verified, since a release PR's failure mode is an omission rather than a bad line:

• Changelog completeness. git log --no-merges b38e9435..origin/master returns exactly those 8 commits, mapping 1:1 onto the 8 added entries — nothing extra, nothing missing, no mis-sectioning. git merge-base origin/master HEAD == origin/master == 910bd1fd, so the section is complete as of the branch's base. b4244907 carries no ! breaking marker, so the single BREAKING CHANGES entry (#687) stays correct.
• The delta touched no manifest, no lockfile, no protos, and no new files — 17 modified .rs files, all under computer/arcbox-computer-runtime. Member count holds at 65, the six first-time crates.io crates are unchanged, and the seventh-new-crate rate-limit threshold is not crossed. Every crate the delta touches is a first-time 0.8.0 publish, so no already-published API breaks.
• Version sweep re-checked. Workspace version and all 53 # x-release-please-version pins at 0.8.0; the three independent cadences (arcbox-hv 0.3.20, arcbox-helper 1.1.0, arcbox-fleet-agent 0.1.4) correctly left off the sweep. Zero 0.7.x remains in Cargo.toml except third-party tokio-util 0.7.18; the only 0.7.0 left in Cargo.lock is the documented third-party rustls-platform-verifier / system-configuration pair.
• Lockfile fidelity. Cargo.lock is a clean 62 + / 62 -, every changed line a standalone version = "0.8.0"; Cargo.toml is 54 changed pairs with zero non-version lines.
• release-please-config.json untouched — draft + force-tag-creation remain on the root package only.

ℹ️ Unlinked-commit count grew 20 → 28

All eight commits in this delta were pushed straight to master without a pull request, so none carries a (#NNN) link — the same process observation as before, now at 28 of 68 entries. None of the new commits touches a manifest or lockfile, and the handover lifecycle work they represent is confined to arcbox-computer-runtime, so this remains a maintainer process note rather than a defect in the release payload. The durable place to describe the new handover behavior for users is the draft release body, which stays editable until the tarball attaches.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/deepseek-ai/deepseek-v4-flash-0731 ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my prior review (e32d340b, seventeenth) is 14 changelog entries plus a date move; the manifest, Cargo.toml, and Cargo.lock are unchanged in shape.

• Fourteen commits that landed on master since the last review joined the 0.8.0 section (82 bullets total, up from 68) — nine Bug Fixes (cd0bdb5/c46ad8b/b193d05 journaling fixes, 507517e/522cc84/7c96ce1 snapshot CoW-device fixes, ef12b7c/db671a9 CI clippy sweeps, 35cfa59 clippy), one Code Refactoring (f3b0788, fc layout), three Tests (286fc55, 55b384b, 7de86bd), and one Feature (595376ff, the process record names the jail its VMM runs in). Each is filed under the section its conventional-commit type implies.
• Release date moved 2026-08-21 → 2026-08-28 — matching today; the compare link is still v0.7.0...v0.8.0.

What I verified, since a release PR's failure mode is an omission rather than a bad line:

• Changelog completeness. git log --no-merges 910bd1fd..origin/master returns exactly those 14 commits, mapping 1:1 onto the 14 added entries — nothing extra, nothing missing, no mis-sectioning. git merge-base origin/master HEAD == origin/master == 55b384b, so the section is complete as of the branch's base.
• The BREAKING CHANGES section correctly still carries only #687. The new feat(vm-driver) (595376ff) carries no ! and no BREAKING CHANGE footer — the JailRecord field is additive and defaults to None, per its own commit body — and f3b0788 is an explicit no-behaviour-change refactor.
• The delta touches no per-crate manifest, no lockfile, and no protos — all 14 commits modify existing files only (.rs plus one workflow and one root-manifest line from ef12b7c, which adds unused_async_trait_impl = "allow" to [workspace.lints.clippy] and changes no dependency graph). Member count holds at 65, the six first-time crates.io crates are unchanged, and the seventh-new-crate rate-limit threshold is not crossed.
• No published API breaks. The delta's only feature touches first-time-publish crates (arcbox-fc-driver, arcbox-vm-driver, arcbox-computer-runtime); the already-published crates it reaches (arcbox-snapshot, arcbox-fs, arcbox-hypervisor, arcbox-virtio-balloon, arcbox-virtio-blk, arcbox-pty, arcbox-net) get only bug fixes and lint appeasement, which a minor bump covers.
• Version sweep re-checked. Workspace version and all 53 # x-release-please-version dep pins at 0.8.0; the three independent cadences (arcbox-hv 0.3.20, arcbox-helper 1.1.0, arcbox-fleet-agent 0.1.4) correctly left off. The lockfile is a clean 62 + / 62 − (65 members − 3 cadences), every changed line a standalone version = "0.8.0"; the only 0.7.0 left in the lock is the documented third-party rustls-platform-verifier / system-configuration pair, and the only 0.7.x in any Cargo.toml is third-party tokio-util 0.7.18.
• release-please-config.json untouched — draft + force-tag-creation remain on the root package only.

One rolling process note, carried forward rather than raised: none of the 14 new commits carries a (#NNN) link, taking the unlinked count from 28 to 42 of 82 entries.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/zai-org/glm-5.3-flash ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my last review (c4bcff35, 2026‑08‑28) is a single generated line: the range‑diff contains only the changelog date move, so this run re‑verified the regenerated release pair against the new master tip rather than re‑reviewing content.

• Release date re‑rendered 2026‑08‑28 → 2026‑09‑11 — release‑please force‑pushes the pair on every master merge and stamps the run date; the 0.8.0 section's 82 bullets are otherwise unchanged.
• .release-please-manifest.json, Cargo.toml and Cargo.lock are byte‑identical to the already‑cleared cut — manifest at 0.8.0 with fleet/sdk entries untouched, 54 changed Cargo.toml pairs (workspace version + 53 pins), a clean 62 + / 62 − lockfile bump, and arcbox-hv 0.3.20 / arcbox-helper 1.1.0 still riding their own cadences.
• Changelog completeness holds under the new master commits — master gained exactly three commits since the last regen (ed5249cf, e2851032, 86f22a89, all feat(fleet-agent) under fleet/), and they are correctly absent from the root changelog: the root package config sets "exclude-paths": ["fleet", "sdk/typescript", "sdk/python"] with "separate-pull-requests": true, so those entries belong to a separate fleet release PR (0.1.4 → 0.2.0 pending there), not this one.

git merge-base origin/master HEAD == origin/master == 86f22a89, so the branch contains all of master, and release-please-config.json — with draft + force-tag-creation on the root package only — is untouched.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/zai-org/glm-5.3-flash ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my last review (c60aeb72, 2026‑09‑11) is one generated changelog bullet: release-please force-pushed the release pair onto the new master tip, and this run re-verified the regenerated files rather than re-reviewing content. Note the usual head-SHA drift: the payload named 60fc3e92, but the reviewed tip is b74c7061 (chore: update lockfiles for release lands after the webhook fires).

• One new ### Miscellaneous Chores entry — **master:** release fleet-agent 0.1.5 (#707) (16be5eb), taking the 0.8.0 section from 82 to 83 bullets. It maps 1:1 onto the single commit master gained since the last regen, and the entry type is long-established in this changelog (the 0.6.x sections carry release fleet-agent 0.1.4 (#638), release sdk-typescript 0.1.3 (#615), release sdk-python 0.1.2 (#580)).
• .release-please-manifest.json — "." → 0.8.0 remains the PR's only manifest change; the fleet entry moved to unchanged context at 0.1.5 because the folded-in master commit is itself the fleet release commit: it bumps fleet in the root manifest plus fleet/CHANGELOG.md and the fleet-agent crate version. The root manifest is not under the root package's exclude-paths, which is exactly why release-please lists the commit in the root changelog. The fleet bump touches a publish = false crate on its own cadence and does not perturb the 0.8.0 cut.
• Cargo.toml and Cargo.lock re-verified byte-clean — 54 changed Cargo.toml pairs (the [workspace.package] version + 53 # x-release-please-version pins) and a clean 62 + / 62 − lockfile, every changed line a standalone version = "0.8.0", zero non-version lines; arcbox-hv 0.3.20 and arcbox-helper 1.1.0 still ride their own cadences as unchanged context.
• Release date and compare link unchanged — still 2026‑09‑11 and v0.7.0...v0.8.0; the BREAKING CHANGES section still carries only #687.

Changelog completeness holds: git log 86f22a89..origin/master returns exactly that one fleet release commit, and git merge-base origin/master HEAD == origin/master == 16be5eb, so the branch contains all of master and the section is complete as of the branch's base. release-please-config.json is untouched. No review threads exist to retire — all nineteen prior reviews were body-only.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/zai-org/glm-5.3-flash ｜ 𝕏}

✅ No new issues found.

Reviewed changes — the delta since my last review (b74c7061, re-rendered as 7f36f7e7 + fc443470 by release-please's force-push) is one generated changelog line; every other changed byte matches what I already cleared.

• CHANGELOG.md — one entry added under ### Bug Fixes: **ci:** let the fleet-agent release builds run to completion (#712, d8f02a6), taking the 0.8.0 section from 83 to 84 bullets (83 type + 1 breaking). Correct section for a fix(ci) type.
• Changelog completeness — git merge-base origin/master HEAD == origin/master == d8f02a6, and master gained exactly one commit since 16be5eb6, mapping 1:1 onto the added entry. The commit touches only .github/workflows/release-fleet-agent.yml (+2/−30), which sits at repo root — outside the root package's exclude-paths — so unlike its fleet/-scoped neighbours it IS listed. Section totals: Features 17, Bug Fixes 27, Code Refactoring 23, Tests 8, Documentation 4, Styles 1, Miscellaneous Chores 3; date 2026-09-11 == today; the BREAKING section still carries only #687; compare link still v0.7.0...v0.8.0.
• Cargo.lock — a clean 62 + / 62 -, every changed line a standalone version = "0.8.0" (62 == 65 workspace members − 3 independent cadences), with zero non-version lines in either direction (machine-checked).
• Cargo.toml — 54 changed pairs (the [workspace.package] version + 53 # x-release-please-version dep pins); every added line carries 0.8.0 and every removed line 0.7.0. arcbox-hv (0.3.20) and arcbox-helper (1.1.0) remain correctly untouched.
• .release-please-manifest.json — the single "." → 0.8.0 bump; fleet 0.1.5, sdk/typescript 0.1.3 and sdk/python 0.1.2 are unchanged context.
• Publish shape carries forward — the folded-in commit is CI-only for the fleet-agent release workflow (job timeout-minutes 30→60 on the macOS matrix and 20→30 on Linux, per-step build caps and both Cache cargo steps removed); it touches no manifest, lockfile, proto, or workspace member, so the member count (65) and the six-new-crates.io-crate set are unchanged, and it cannot perturb the 0.8.0 publish (release.yml untouched).
• release-please-config.json untouched — not among the four changed files, so draft + force-tag-creation remain on the root package only.

No review threads required retirement — the prior review, like all twenty before it, was body-only.

  ^{｜ View workflow run ｜ Using openai-compatible/@cf/zai-org/glm-5.3-flash ｜ 𝕏}